Overview
What is Azure DevOps Server?
AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server)…
Azure DevOps is a game change
Agile project management with automation and tracking.
Azure DevOps Server: All-in-one and High Performance Agile Tool
Azure DevOps Server- A Collaborative tool for productivity
A non-developer's thoughts
Manage and automate Software Development End2End.
Sure about Azure...DevOps
Engineering Based Toolset for Extreme Collaboration
All-in-one solution with stability
Software Management and Agile Project Management in One Package
Azure DevOps for a SAFe based, SOC2 Type 2 audited, heterogenous cloud microservices SDLC / ALM
Good Agile Management Tool
Still TFS to Me
TFS is an excellent tool to support the full ALM
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
What is Azure DevOps Server?
AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine…
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
36 people also want pricing
Alternatives Pricing
What is Azure DevOps Services?
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
What is CircleCI?
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so…
Product Details
- About
- Tech Details
- FAQs
What is Azure DevOps Server?
Azure DevOps Server Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(280)Attribute Ratings
Reviews
(1-25 of 31)A great product for CI/CD
- Continuous integration
- Continuous development
- Project management
- Ease of usage
- More integration with open source
- Navigation
Azure DevOps is a game change
- Azure Boards is fast to use once you have a good structure in place. You can create or modify each task type quickly. The consequence of that is that is it reduces your admin overhead so its a no-brainer to create lots of smaller tasks.
- Azure Repos is simple to set up compared to other on prem solutions that we have used. Most options come out of the box including user management.
- The Pipelines tool is very powerful, and you can quickly create your CI/CD pipelines. Simple to see the state of each pipeline at a glance.
- Azure Boards can be daunting to set up. There are a lot of different features and if you don't know what you are doing it's easy to overcomplicate things.
- If you have lots of similar Pipelines to create there is no way to template them, each one has to be created and managed separately. So if your target K8s cluster changes, you have to manually edit each Pipeline.
- Simple tracking of progress throughout the project.
- Perform project management duties with superior ability to set priorities and approve work.
- In order to ensure that all of the project's requirements are met, a thorough test plan is necessary.
- It doesn't work well with tools from other companies.
- Improvements can be made to the user interface to make it more natural to use.
- I also think capacity planning may use some fine-tuning.
- You can integrate it effortlessly with almost all Microsoft products
- Supports Agile and can be used for version control
- Bug tracking
- Ease of use
- I feel that because it's a Microsoft product, it integrates better with other Microsoft products too. Since mine is more of a Microsoft-based company, it's not a problem for me, but for others, you might want to consider this before making any decision
- The user interface could have been better
- Agile boards can be better
Azure DevOps Server was very helpful to our teams while we started working remotely, helped in increasing the productivity and prototyping the projects for release without any delay. Best part of using this tool is reporting, we were able to create Kanbans dashboards for integrated reports.
- Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
- Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
- Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
- Azure test plans can be improved to be more automated, existing generic templates can be added to create more test plan in different languages.
It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects.
Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate.
A non-developer's thoughts
- Resource management
- Sprint planning
- Organising requirements
- Could use a more intuitive interface
- On-screen demo/tips would be helpful for new users
Sure about Azure...DevOps
- Organizes tasks with space for all the added context one would need (requirements, design links, etc.)
- Ability to capture a backlog of items to better visualize a roadmap to help with planning/prioritizing.
- Streamlines the work being done across a large project team with various specialists.
- Intuitive to use with minimal learning curve for those new to the tool.
- It is very utilitarian looking, maybe consider a more personable UI aesthetic
Engineering Based Toolset for Extreme Collaboration
- Version control
- Requirements definition
- Secrets library management
- Continuous integration and deployment
- Wiki Markdown customization
- Better Syntax Highlighter in Repository
- Improvements in Requirements Definition Customization
- Azure DevOps easily handles our source code and works seamlessly with Visual Studio (our main development environment).
- Our business analysts use its features to document and assign user stories for Agile-based projects.
- Our deployment team uses Azure DevOps to push code from development to main to user acceptance and finally production.
- For managing Agile projects, web-based navigation is terrible. There's no easy drop-down menu system you have to hunt and peck around to try and find pages to manage your hours.
- Our management needs the ability to predict when development may finish a project. Azure DevOps fails here because it doesn't easily provide a feature to let you predict an end date and it doesn't easily provide you with a feature to export the data to Excel so you could plug-in a formula to calculate an end date.
- The menu options for code management are sparse. It would be great if they had a feature to let you simply drag and drop folder structures.
Good Agile Management Tool
- User story management
- Integrations with other products
- Reporting
- It does not necessarily play very well with non-Microsoft stacks
- Upgrades have been cumbersome; however, with the cloud offering, that is mostly off the table as a major issue
- Some of the search functionality is unclear and difficult to use
- Could have more pre-built templates; it offers so much it can be challenging at times
Still TFS to Me
- Orginazation
- Notifications
- Complex nesting of projects
- So many options, getting the team on the same page
- Formatting
- Tricky for new users
TFS is an excellent tool to support the full ALM
- Linking together all aspects of the application life cycle, from requirements to code to builds and test.
- Trace-ability of all application life cycle via reports and queries.
- Automated testing.
- Flexibility of source code management. Centralized or distributed.
- Upgrade paths could be handled better. Very difficult to upgrade with customization in place.
- Capacity planning could be improved.
- Dot Net framework 260 character path limit is ridiculous.
Azure DevOps Server: Used at our Org for IT Purposes!
- Organization
- Defect tracking
- Severity
- Escalation
- Issue/user traceability
- Easier interface.
- Less drop downs and tabs.
- Email notifications.
Happy User of Azure DevOps Server
- Organization of tasks per team member
- Statistics provider for data related to capacity and output
- Good UX/UI experience for clarity
- Copy/Paste functionality could be improved
- Ability to see all team members more clear visually
- Sort feature on columns could be better
It would be less appropriate for small projects that do not need maintained history or have a very small group of people working on them.
Azure DevOps server is a great product
- Git integration has been fantastic.
- Provides a convenient UI for managing the SCRUM process.
- Built-in Code Review feature and completion policies.
- I wish I could default to a specific dashboard on load.
Take an advantage of Microsoft TFS for easy integration with other Microsoft family products
- TFS makes it easier to build technical features and acceptance criteria that different team members of Product Manager, Engineering, Quality Assurance, and Release Management.
- It enables the product managers to review technical backlog, prioritize features and go to market that helps improve key performance indicators.
- It provides seamless integration with Microsoft products like SharePoint, IIS, Visual Studio that helps integrate and exchange data.
- TFS UI could improve like some of its major competitors with fewer options on the same UI page. TFS tries to offer too many options on the same UI.
- Development in branches is hard to achieve and TFS has a room for improvement.
- Integration with non-Microsoft is difficult. TFS could provide easier integration with other product lines to improve acceptability.
- Easier to build a technical backlog.
- Create user stories, features, EPICs, assign tasks and acceptance criteria, etc.
- Make a Product Manger's and engineering teams' life easier in meeting and tracking.
- Project managers can easily track the work and create reporting.
Code versioning tool with room for improvement
- Integration with Microsoft products, like SharePoint, IIS, Visual Studio
- Users are able to access via desktop client, web browser and through Visual Studio
- Code version control
- Bad UX and UI in the web interface
- Merging code is a very hard task
- Development in branches is also hard to achieve
- Not so easy to upgrade server version
Great system for consolidating work and information
- The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
- Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
- Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.
- Searching through code can be somewhat cumbersome. It would be nice if there was a way to do general searches in certain areas of the system.
- Without proper training, the system can be confusing to navigate. This issue can be prevented with good training but it is something to be aware of.
- Navigation can be clunky at times depending on where you are in the system. For power users, this is not a huge deal but it is a tad bit annoying.
I like to work with Team Foundation Server
- I like the Team Foundation Source Control Management much more compared to other Systems like GIT, because:
- - Perfect Integration into Visual Studio
- - Easy and direct checkout/check-in
- - Perfect branching and merging
- - Workflow Support with autmated Reminders
- The Build System is just great. Since Version 2017 its very easy to integrate self made tools into the build process.
- Easy Managament of Users and User Rights.
- Team Foundation Server could be improved in the Task and Backlog Managment for smaller Teams. E.G.: It's hard to quickly write down Tasks during a meeting because you have to fill in lots of Fields per WorkItem. It is hard to push the Items around.
TFS is great for a Microsoft Shop
- Continuous integration when the team is using azure is really easy.
- It's fairly intuitive to use.
- Azure or IIS deployment is very easy.
- The project management/scrum piece is hard to learn.
- The Wikipedia functionality it provides isn't very useful for lack of features.
- It takes a REALLY long time to check in a large number of newly added files.
- If your file paths get too long, TFS gives you errors.
You could use some other source control with .NET but it integrates so well with the rest of the Microsoft family and is so reasonably priced, there'd be no need to.
TFS is useful for big projects... as long as you know it already
- Traceability between MS Suite
- Clear what's a Bug, User Story, Feature, Epic
- Linking test cases
- Bad use of real estate is it's No. 1 failing, why all the white space?
- Too much functionality makes it difficult for new users to jump onboard - it's daunting at first
- Configuring dashboards is easy, but not necessarily what you want to show to upper management - needs some tweaking
TFS - The complete Development Tool
- Work Item tracking - The ability to define the flow of your work items to match your development/test process is really valuable
- Version Control - The ability to easily track changes between every checked in version of source code can be a life saver
- Project Management - The project management dashboards showing things like burndown enables us to easily track whether we are on target for a release
- Integration between our help desk system and TFS was possible but not as easy as I would expect considering both are Microsoft products
- Advanced reporting for dashboards could be made easier
Is TFS the right tool?
- TFS has an excellent interactive UI for all users to make source control easy to use.
- TFS has the backing of a major company, Microsoft. Updates and the way it is used gets regular updates.
- TFS integrates into Visual Studio.
- TFS has many tools for many different areas in the development life cycle.
- There is no real ability to work offline. You need to be actively connected to it in order to see history.
- Having many hands in the same project/file can cause conflicts that can be hard to resolve.
- having a "master" branch is difficult in TFS, it can be done but it is slow and cumbersome and not an intuitive process.
TFS - A Truly Functional System
- Automatic generation of burn down chart
- Easy to link user stories and tasks across
- Easy to move tasks across user stories
- Easy to move user stories across sprints
- There are issues encountered when uploading more than one attachment to a task. One needs to refresh first then save.
- The Admin function where you add iterations isn’t very user-friendly.
TFS = meh
- Project management
- Scrum
- Integration with visual studio
- Not a user friendly implementation of Git
- TFS version control is not widely used in favor of Git